<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- /fasttmp/mkdist-qt-4.3.5-1211793125/qtopia-core-opensource-src-4.3.5/doc/src/deployment.qdoc -->
<head>
  <title>Qt 4.3: Deploying Qt Applications</title>
  <link href="classic.css" rel="stylesheet" type="text/css" />
</head>
<body>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td align="left" valign="top" width="32"><a href="http://www.trolltech.com/products/qt"><img src="images/qt-logo.png" align="left" width="32" height="32" border="0" /></a></td>
<td width="1">&nbsp;&nbsp;</td><td class="postheader" valign="center"><a href="index.html"><font color="#004faf">Home</font></a>&nbsp;&middot; <a href="classes.html"><font color="#004faf">All&nbsp;Classes</font></a>&nbsp;&middot; <a href="mainclasses.html"><font color="#004faf">Main&nbsp;Classes</font></a>&nbsp;&middot; <a href="groups.html"><font color="#004faf">Grouped&nbsp;Classes</font></a>&nbsp;&middot; <a href="modules.html"><font color="#004faf">Modules</font></a>&nbsp;&middot; <a href="functions.html"><font color="#004faf">Functions</font></a></td>
<td align="right" valign="top" width="230"><a href="http://www.trolltech.com"><img src="images/trolltech-logo.png" align="right" width="203" height="32" border="0" /></a></td></tr></table><h1 align="center">Deploying Qt Applications<br /><small></small></h1>
<p>Deploying an Qt application does not require any C++ programming. All you need to do is to build Qt and your application in release mode, following the procedures described in this documentation. We will demonstrate the procedures in terms of deploying the <a href="tools-plugandpaint.html">Plug &amp; Paint</a> application that is provided in Qt's examples directory.</p>
<p>There are two ways of deploying an application:</p>
<ul>
<li>Static Linking</li>
<li>Shared Libraries (Frameworks on Mac)</li>
</ul>
<p>Static linking results in a stand-alone executable. The advantage is that you will only have a few files to deploy. The disadvantages are that the executables are large and with no flexibility (i.e a new version of the application, or of Qt, will require that the deployment process is repeated), and that you cannot deploy plugins.</p>
<p>To deploy plugin-based applications, you can use the shared library approach. Shared libraries also provide smaller, more flexible executables. For example, using the shared library approach, the user is able to independently upgrade the Qt library used by the application.</p>
<p>Another reason why you might want to use the shared library approach, is if you want to use the same Qt libraries for a family of applications. In fact, if you download the binary installation of Qt, you get Qt as a shared library.</p>
<p>The disadvantage with the shared library approach is that you will get more files to deploy.</p>
<p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<thead><tr valign="top" class="qt-style"><th colspan="5">Qt's Libraries</th></tr></thead>
<tr valign="top" class="odd"><td><a href="qtcore.html">QtCore</a></td><td><a href="qtgui.html">QtGui</a></td><td><a href="qtnetwork.html">QtNetwork</a></td><td><a href="qtopengl.html">QtOpenGL</a></td><td><a href="qtsql.html">QtSql</a></td></tr>
<tr valign="top" class="even"><td><a href="qtsvg.html">QtSvg</a></td><td><a href="qtxml.html">QtXml</a></td><td><a href="qtdesigner.html">QtDesigner</a></td><td><a href="qtassistant.html">QtAssistant</a></td><td><a href="qt3support.html">Qt3Support</a></td></tr>
</table></p>
<p>Since Qt is not a system library, it has to be redistributed along with your application; the minimum is to redistribute the run-time of the libraries used by the application. Using static linking, however, the Qt run-time is compiled into the executable.</p>
<p>In particular, you will need to deploy Qt plugins, such as JPEG support or SQL drivers. For more information about plugins, see the <a href="plugins-howto.html">How to Create Qt Plugins</a> documentation.</p>
<p>When deploying an application using the shared library approach you must ensure that the Qt libraries will use the correct path to find the Qt plugins, documentation, translation etc. To do this you can use a <tt>qt.conf</tt> file. For more information, see the <a href="qt-conf.html">Using qt.conf</a> documentation.</p>
<p>Depending on configuration, compiler specific libraries must be redistributed as well. For more information, see the platform specific Application Dependencies sections: <a href="deployment-x11.html#application-dependencies">X11</a>, <a href="deployment-windows.html#application-dependencies">Windows</a>, <a href="deployment-mac.html#application-dependencies">Mac</a>.</p>
<p>The procedure of deploying Qt applications is different for the various platforms:</p>
<ul>
<li><a href="deployment-x11.html">Qt/X11</a></li>
<li><a href="deployment-windows.html">Qt/Windows</a></li>
<li><a href="deployment-mac.html">Qt/Mac</a></li>
<li><a href="qtopiacore-deployment.html">Qtopia Core</a></li>
</ul>
<p>See also <a href="installation.html">Installation</a> and <a href="winsystem.html">Window System Specific Notes</a>.</p>
<p><table width="100%" class="annotated" cellpadding="2" cellspacing="1" border="0">
</table></p>
<p /><address><hr /><div align="center">
<table width="100%" cellspacing="0" border="0"><tr class="address">
<td width="30%">Copyright &copy; 2008 <a href="trolltech.html">Trolltech</a></td>
<td width="40%" align="center"><a href="trademarks.html">Trademarks</a></td>
<td width="30%" align="right"><div align="right">Qt 4.3.5</div></td>
</tr></table></div></address></body>
</html>
